Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1952

reference
34-tree-1
name
1952
tree-preservation-order

undefined

34-tpo-1
uprn
address-text
point
POINT (-0.950985 50.850409)
geometry
MULTIPOLYGON (((-0.950928 50.850403,-0.950930 50.850414,-0.950938 50.850424,-0.950951 50.850433,-0.950966 50.850438,-0.950984 50.850440,-0.951002 50.850438,-0.951017 50.850433,-0.951030 50.850425,-0.951038 50.850415,-0.951042 50.850404,-0.951039 50.850393,-0.951031 50.850383,-0.951019 50.850375,-0.951003 50.850370,-0.950986 50.850368,-0.950968 50.850369,-0.950952 50.850374,-0.950939 50.850382,-0.950931 50.850392,-0.950928 50.850403)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL